Initiating a call to an emergency call center via a relay service

ABSTRACT

A call to an emergency call center from a device is initiated utilizing a relay service. The device may send a non-voice message to the relay service. The relay service, upon receipt and analysis of the message, may initiate a call to the device. The device, upon receiving the call and determining that the call is from the relay service, may place the call on hold and initiate a call to an emergency call center. Subsequently, the device may establish a multi-party call between the device, the relay service, and the emergency call center. Further, the relay service may maintain multiple communications modes in order to conduct non-voice messages with the device and conduct voice communications with the emergency call center.

TECHNICAL FIELD

The technical field generally relates to public safety, and morespecifically relates to initiating a call to an emergency call center,and even more specifically relates to initiating a call to an emergencycall center via a relay center.

BACKGROUND

In an emergency situation, an individual can call 9-1-1 in order toobtain a quick response. The person can explain the emergency situationto the 9-1-1 call taker, and the 9-1-1 call taker can dispatchappropriate personnel to handle the emergency. This may be difficult, ifnot impossible, for a person with an impaired physical ability. Forexample, a person with a hearing impairment and/or speech impairment maynot be able to speak to a 9-1-1 call taker to describe the emergencysituation.

SUMMARY

The following presents a simplified summary that describes some aspectsand/or embodiments of the subject disclosure. This summary is not anextensive overview of the disclosure. Indeed, additional or alternativeaspects and/or embodiments of the subject disclosure may be availablebeyond those described in the summary.

A relay service is utilized to initiate a call to an emergency callcenter. In an example embodiment, a message is sent from a device to arelay service. The message may be in the form of a text message, amessage comprising video, an instant messaging-like message, a ShortMessage Service (SMS) message, a Multimedia Messaging Service (MMS)message, a web chat, or the like. The relay service, upon receipt andanalysis of the message, may initiate a call to the device from whichthe message was sent. The device, upon receiving the call anddetermining that the call is from the relay service, may place the callon hold and initiate a call to an emergency call center. Subsequently,the device may establish a multi-party call between the device, therelay service, and the emergency call center. The relay center mayconduct message communications with the device and the relay center mayconduct voice communications with the emergency call center.

Accordingly, a person with an impaired ability to initiate and/orconduct a call to an emergency call center, may utilize a relay serviceas described herein, to avoid delays in contacting an emergency callcenter. The mechanisms utilized by the device may be transparent to theperson. Further, as described herein, the emergency call center and/orthe relay center may be able to listen to and/or record audio from thedevice.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale.

FIG. 1 illustrates an example system and process for initiating anemergency call.

FIG. 2 illustrates another example system and process for initiating anemergency call.

FIG. 3 is a flow diagram of an example process for initiating a call toan emergency call center via a relay center.

FIG. 4 is a block diagram of an example wireless communications devicethat is configurable to initiate a call to an emergency call center.

FIG. 5 is a block diagram of an example relay service server.

FIG. 6 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichinitiation of a call to an emergency call center may be implemented.

FIG. 7 illustrates an architecture of a typical GPRS network in whichinitiation of a call to an emergency call center may be implemented.

FIG. 8 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within which initiation of a call to anemergency call center may be implemented.

FIG. 9 illustrates a PLMN block diagram view of an exemplaryarchitecture in which initiation of a call to an emergency call centermay be incorporated.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1 illustrates an example system and process for initiating anemergency call. As depicted in FIG. 1, a user (e.g., subscriber) 12,wants to make an emergency call to an emergency call center, for example(e.g., to 9-1-1). The user 12 can initiate a call via a communicationsdevice 14, to a relay service center 18, via a wireless network 16. Thecall can be in the form of any appropriate call. In an exampleembodiment, the call may be in the form of a text message, a messagecomprising video, an instant messaging-like message, a Short MessageService (SMS) message, a Multimedia Messaging Service (MMS) message, aweb chat, or the like. The user 12 may start an application that haspreviously been installed on his/her communications device 14. Theapplication can provide the user 12, via a user interface, or the like,on the communications device 14, the option to initiate a non-voicebased (e.g., text based) session. In an example configuration, a textbased session may automatically be initiated via preferences in theuser's profile. The user 12 may compose a non-voice message utilizingSMS, IM, email, or the like, or a combination thereof. The user 12, viathe communications device 14, may assign the message a special shortcode or telephone number that may be designated for non-voice to 911emergency messages.

At steps 26 and 28, the communications device 14 may send the message tothe relay center 18 via the wireless network 16 (e.g., radio accessnetwork or the like). The relay service center 18 may comprise a relayservice center server 24. The relay service center server 24 maycomprise any server, processor, computer, or the like, or anyappropriate combination thereof. In various example embodiments, therelay service center server 24 may be configured to receive and/or sendmessages, analyze messages, provide an indication of a message to relayservice personnel, or any appropriate combination thereof. Upon receiptand analysis of the message at the relay service center 18, it may bedetermined that an emergency condition exists. Examples of emergencyconditions may include life threatening health condition (e.g., heartattack) being experienced by the subscriber, life threatening healthcondition occurring to another individual near the location of thesubscriber (e.g., spouse, child, neighbor, friend), fire in the locationof the subscriber, fire in the neighboring buildings of the subscriber'slocation, intruder in the subscriber's home, break-in observed atneighbor's home, automobile accident experienced by the subscriber, andautomobile accident observed by the subscriber. The determination may beaccomplished via the relay service center server 24, a relay servicecenter person, or any appropriate combination thereof. The message maybe analyzed in any appropriate manner to determine if an emergencycondition exists. For example this may be determined from content in thebody of the message, a header of the message, an identifier embedded inthe message, a designated field of the message, video contained in themessage, a graphic contained in the message, or the like, or anyappropriate combination thereof.

Upon determining that that an emergency condition exists, the relayservice center 18 calls the communications device 14 via the wirelessnetwork 16 (steps 30 and 32). The communications device 14, uponreceiving the call (from steps 30 and 32) may determine that the calloriginated from the relay service center 18. This determination may beaccomplished via any appropriate means. For example, the communicationsdevice 14 may interpret a caller ID mechanism to determine that the calloriginated from relay service center, the communications device 14 mayinterpret an indicator that was incorporated in the call by the relayservice center 18 (e.g., indicator that the call is a 9-1-1 relatedcall, etc.), or any appropriate combination thereof. In an exampleembodiment, in-band signaling may be accomplished via the use of DTMFtones. After a voice circuit has been established between the relayservice center 18 and the subscriber's communications device 14, therelay service center server 24 would send to the communications device14 the in-band signaling code (e.g., #911) via DTMF tones. Thecommunications device 14 would be monitoring the established voicecircuit for DTMF tones and would recognize the #911 in-band signalingcode and would determine that this call is from the relay service center18.

Upon determining that the call (from steps 30 and 32) is from a relayservice center, the communications device 14 may place the relay servicecenter on hold and initiate a call to an emergency call center. In anexample embodiment, the call to an emergency call center may be a 9-1-1call to emergency call center 22, at step 34, 36, and 38, via wirelessnetwork 16 and public switched telephone network 20. The emergency callcenter may comprise any appropriate emergency call center such as, forexample, a PSAP, a fire department, a police station, a public safetyoffice, or the like. The call to the emergency call center 22 can beinitiated via any appropriate means for initiating a call to anemergency call center (e.g., 9-1-1 call, call to another number such asfire station, police department, etc., or the like). In an exampleembodiment, the call to the emergency call center 22 may be a 9-1-1 callthat utilizes established mechanisms for location determination and PSAProuting. In the wireless network 16, there may be configurationinformation that associates every cell site with an appropriate PublicSafety Answering Point (PSAP) including instructions on how to addressand route calls to that specific PSAP. When an emergency call isinitiated by the communications device 14, the wireless network 16 maybe instructed, via call set-up signaling, that this is an emergencycall. As part of the call set-up processing, the wireless network 16 mayknow which cell site is connected to the communications device 14(commonly called the serving cell). Using the identity of the servingcell, the wireless network 16 may use its internal configurationinformation to determine the PSAP associated with the serving cell.Using the call routing instructions of the associated PSAP, theemergency voice call is established between the communications device 14and the emergency call center 22 (also known as a PSAP).

When the call from the communications device 14 is answered by emergencycall center 22, the communications device 14 may establish a multi-partycall. In an example embodiment, the multi-party call may be between therelay service center 18 and the emergency call center 22. In anotherexample embodiment, the multi-party call may be between thecommunications device 14, the relay service center 18, and the emergencycall center 22, as depicted by dashed arrows 40. For example, thecommunications device 14 may establish a conference call between thecommunications device 14, the relay service center 18, and the emergencycall center 22. The relay service center 18 may conduct voicecommunications with the emergency call center 22. Thus, even if the user12 is unable to speak or hear, the call taker at the emergency callcenter 22 will be able receive background audio and/or video from theenvironment of the user 12. This background audio and/or video mayprovide information to the call taker at the emergency call center 22 toassess the urgency and severity of the emergency and to distinguishbetween actual emergency calls and prank calls. In an exampleembodiment, the relay service center 18 may maintain separatecommunications (separate from the multi-party call 40) in order toreceive messages from the communications device 14 and provide messagesto the communications device 14.

Thus, the relay service center 18 may be in concurrent non-voice andvoice communications as depicted in FIG. 2. That is, the relay servicecenter 18 may be in concurrent non-voice communication with thecommunications device 14, and voice communication with thecommunications device 14 and the emergency call center 22. Accordingly,a call taker at the relay service center 18 may communicate with theuser 12 via a first communications mode (e.g., non-voice communications)and relay the communications to a call taker at the emergency callcenter 22 via a second communications mode (e.g., voice communications).And the call taker at the relay service center 18 may communicate with acall taker at emergency call center 22 via the second communicationsmode (e.g., voice communications) and relay the communications to theuser 12 via the first communications mode (e.g., non-voicecommunications).

As a result of the foregoing described process, delays in contactingemergency call centers (e.g., PSAPs) may be mitigated or eliminated.Emergency call centers may be able to record audio and/or video from thecommunications device. The recorded information may be utilized asneeded (e.g., for use in trials, as evidence, etc.). Existingmethodologies for location determination and PSAP routing may beutilized. And, the user 12 may use the communications device as he/shewould normally use the commutations device to make a 9-1-1 call. Theunderlying process may be transparent to the user 12.

FIG. 3 is a flow diagram of an example process for initiating a call toan emergency call center via a relay center. A message is generated atstep 42. The message may be generated by any appropriated device, suchas, for example, a communications device, or the like. In an exampleembodiment, the message may be in the form of a text message, a videomessage, an instant messaging-like message, a Short Message Service(SMS) message, a Multimedia Messaging Service (MMS) message, web chat,or the like. In an example configuration, a text based session mayautomatically be initiated via preferences in a user's profile. The usermay compose a non-voice message utilizing SMS, IM, email, or the like,or a combination thereof. The user may assign the message a specialshort code or telephone number that may be designated for non-voice to9-1-1 emergency messages.

The message is provided to an intended recipient at step 44. In anexample embodiment, the intended recipient is a relay service. The relayservice may analyze the message to determine if an emergency conditionexists at step 46. The determination may be accomplished in anappropriate manner, such as, for example from analyzing content in thebody of the message, analyzing a header of the message, analyzing anidentifier embedded in the message, analyzing a designated field of themessage, analyzing video contained in the message, analyzing a graphiccontained in the message, or the like, or any appropriate combinationthereof. If it is determined that an emergency condition does not exist(at step 46), the process ends at step 48.

If it is determined that an emergency condition does exist (at step 46),a call is initiated by the relay service, at step 50. The call may besent to the device that sent the message. The device may receive thecall from the intended recipient (e.g., relay service) of the message atstep 52. Thus, receipt of the call by the device is indicative of adetermination (by the recipient of the message) that an emergencycondition exists. The received call is analyzed, at step 54, todetermine if it originated from the relay service. This determinationmay be accomplished via any appropriate means, such as, for example, acaller ID mechanism may be interpreted, an indicator that wasincorporated in the call by the relay service (e.g., indicator that thecall is a 9-1-1 related call, etc.) may be interpreted, or anyappropriate combination thereof.

If it is determined, at step 56, that the call was not sent by the relayservice, the process ends at step 58. If it is determined, at step 56,that the call was sent by the relay service, the call may be placed onhold, at step 60, by the device that received the call. A call to anemergency call center may be initiated at step 62. A multi-party callmay be initiated at step 64. The multi-party call may be establishedbetween the device that sent the message (step 44), the relay service,and the emergency call center. For example, a conference call may beestablished between the device, the relay service, and the emergencycall center.

In an example embodiment, multiple communication modes may be maintainedat step 66. For example, the relay service may maintain separatecommunications (separate from the multi-party call) in order to receivemessages from the device and provide messages to the device. Thus, therelay service may be in concurrent non-voice communication with thedevice and voice communication with the device and the emergency callcenter. Accordingly, a call taker at the relay service may communicatewith a user of the device via a first communications mode (e.g.,non-voice communications) and relay the communications to a call takerat the emergency call center via a second communications mode (e.g.,voice communications). And the call taker at the relay service maycommunicate with a call taker at emergency call center via the secondcommunications mode (e.g., voice communications) and relay thecommunications to the user via the first communications mode (e.g.,non-voice communications).

FIG. 4 is a block diagram of an example wireless communications device70 that is configurable to initiate a call to an emergency call center.In an example embodiment, the communication device 70 may comprise thecommunications device 14 described herein. The communications device 70may include any appropriate device, mechanism, software, and/or hardwarefor initiating a call to an emergency call center as described herein.As described herein, the communications device 70 may comprise hardwareor a combination of hardware and software. In an example configuration,the communications device 70 may comprise processing circuitry 72,memory circuitry 74, input/output circuitry 76, user interface (UI)circuitry 78, and sensor circuitry 80 comprising at least one of a videocamera portion 82, a force/wave sensor 84, a microphone 86, a moisturesensor 88, or a combination thereof. The force/wave sensor may compriseat least one of a motion detector, an accelerometer, an acoustic sensor,a tilt sensor, a pressure sensor, a temperature sensor, or the like. Themotion detector may be configured to detect motion occurring outside ofthe communications device, for example via disturbance of a standingwave, via electromagnetic and/or acoustic energy, or the like. Theaccelerator may be capable of sensing acceleration, motion, and/ormovement of the communications device. The acoustic sensor may becapable of sensing acoustic energy, such as a loud noise, for example.The tilt sensor may be capable of detecting a tilt of the communicationsdevice. The pressure sensor may be capable of sensing pressure againstthe communications device, such as from a shock wave caused by brokenglass or the like. The temperature sensor may be capable of sensing ameasuring temperature, such as inside of the vehicle, room, building, orthe like. The moisture sensor 88 may be capable of detecting moisture,such as detecting if the communications device 70 is submerged in aliquid. The processing circuitry 72, memory circuitry 74, input/outputcircuitry 76, user interface (UI) circuitry 78, video camera portion 82,force/wave sensor 84, and microphone 86 may be coupled together to allowcommunications therebetween (coupling not shown in FIG. 4). Thecommunications device may comprise a timer (not depicted in FIG. 4).

In various embodiments, the input/output circuitry 76 comprises areceiver of the communications device 70, a transmitter of thecommunications device 70, or a combination thereof. The input/outputcircuitry 76 is capable of receiving and/or providing informationpertaining to initiating a call to an emergency call center as describedherein. The input/output circuitry 76 also may be capable ofcommunications with the wireless network 16, the relay service center18, the relay service center server 24, and/or the emergency call center22, as described herein. For example, the input/output circuitry 76 mayinclude a wireless communications (e.g., 2.5G/3G/4G) SIM card. Theinput/output circuitry 76 may be capable of receiving and/or sendingvideo information, audio information, control information, imageinformation, data, or any combination thereof. In an example embodiment,the input/output circuitry 76 may be capable of receiving and/or sendinginformation to determine a location of the communications device 70. Inan example configuration, the input\output circuitry 76 may comprise aGPS receiver. In an example configuration, the communications device 70may determine its own geographical location through any type of locationdetermination system including, for example, the Global PositioningSystem (GPS), assisted GPS (A-GPS), time difference of arrivalcalculations, configured constant location (in the case of non-movingdevices), any combination thereof, or any other appropriate means. Invarious configurations, the input/output circuitry 76 may receive and/orprovide information via any appropriate means, such as, for example,optical means (e.g., infrared), electromagnetic means (e.g., RF, WI-FI,BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or any appropriatecombination thereof. In an example configuration, the input/outputcircuitry may comprise a WIFI finder, a two way GPS chipset orequivalent, or the like.

The processing circuitry 72 may be capable of facilitating initiation ofa call to an emergency call center as described herein. For example, theprocessing circuitry 72 may be capable of, in conjunction with any otherportion of the communications device 70, executing an application forinitiating a call to an emergency call center, generating a non-voicemessage, generating a voice message, communication with a relay servicecenter via a text message and/or voice message, communication with anemergency call center via a text message and/or voice message,processing a received text message, processing a received voice message,processing a retrieved text message, processing a retrieved voicemessage, generating a predetermined message, retrieving a predeterminedmessage, processing non-voice messages provided via the user interfacecircuitry 78, processing voice messages provided via the user interfaceportion 78, processing text messages received via the input/outputcircuitry 76, processing voice messages received via the input/outputcircuitry 76, determining if an emergency condition exists, analyzing acall to determine if the call originated from a relay service, placing acall on hold, establishing a multi-party call, or the like, or anycombination thereof. The processing circuitry 72, in conjunction withany other portion of the communications device 70, may provide theability for users/subscribers to enable, disable, and configure variousfeatures of an application for initiating a call to an emergency callcenter, as described herein. For example, a user, subscriber, parent,healthcare provider, law enforcement agent, of the like, can defineconfiguration parameters such as, for example, an emergency contactlist, voice/text/image/video options for an emergency call, thresholdsettings (e.g., timer settings, signature settings, etc.), to beutilized when sending and/or receiving a text/voice message to/from anemergency call taker/relay service. The processing circuitry 72, inconjunction with any other portion of the communications device 70, mayenable the communications device 70 to covert speech to text when it isconfigured to send text messages. In an example embodiment, theprocessing circuitry 72, in conjunction with any other portion of thecommunications device 70, may be able to convert text to speech forrendering via the user interface circuitry 78.

In a basic configuration, the communications device 70 may include atleast one memory circuitry 74. The memory circuitry 74 may be able storeany information utilized in conjunction with initiating a call to anemergency call center as described herein. For example, the memorycircuitry 74 may be capable of storing information pertaining toexecuting an application for initiating a call to an emergency callcenter, generating a non-voice message, generating a voice message,communication with a relay service center via a text message and/orvoice message, communication with an emergency call center via a textmessage and/or voice message, processing a received text message,processing a received voice message, processing a retrieved textmessage, processing a retrieved voice message, generating apredetermined message, retrieving a predetermined message, processingnon-voice messages provided via the user interface circuitry 78,processing voice messages provided via the user interface portion 78,processing text messages received via the input/output circuitry 76,processing voice messages received via the input/output circuitry 76,determining if an emergency condition exists, analyzing a call todetermine if the call originated from a relay service, placing a call onhold, establishing a multi-party call, or the like, or any appropriatecombination thereof. Depending upon the exact configuration and type ofprocessor, the memory circuitry 74 may be volatile (such as some typesof RAM), non-volatile (such as ROM, flash memory, etc.). Thecommunications device 70 may include additional storage (e.g., removablestorage and/or non-removable storage) including, tape, flash memory,smart cards, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, universal serial bus (USB) compatiblememory, or the like. In an example configuration, the memory circuitry74, or a portion of the memory circuitry 72 may hardened such thatinformation stored therein can be recovered if the communications device70 is exposed to extreme heat, extreme vibration, extreme moisture,corrosive chemicals or gas, or the like. In an example configuration,the information stored in the hardened portion of the memory circuitry74 may be encrypted, or otherwise rendered unintelligible without use ofan appropriate cryptographic key, password, biometric (voiceprint,fingerprint, retinal image, facial image, or the like). Wherein, use ofthe appropriate cryptographic key, password, biometric may render theinformation stored in the hardened portion of the memory circuitry 74intelligible.

The communications device 70 also may contain UI circuitry 78 allowing auser to communicate with the communications device 70. The UI circuitry78 may be capable of rendering any information utilized in conjunctioninitiating a call to an emergency call center as described herein. Forexample, the UI circuitry 78 may contain circuitry for entering text,entering a phone number, rendering text, rendering images, renderingmultimedia, rendering sound, rendering video, receiving sound, or thelike, as described herein. The UI circuitry 78 may provide the abilityto control the communications device 70, via, for example, buttons, softkeys, voice actuated controls, a touch screen, movement of the mobilecommunications device 70, visual cues (e.g., moving a hand in front of acamera on the mobile communications device 70), or the like. The UIcircuitry 78 may provide visual information (e.g., via a display), audioinformation (e.g., via speaker), mechanically (e.g., via a vibratingmechanism), or a combination thereof. In various configurations, the UIcircuitry 78 may comprise a display, a touch screen, a keyboard, aspeaker, or any combination thereof. The UI circuitry 78 may comprisecircuitry for inputting biometric information, such as, for example,fingerprint information, retinal information, voice information, and/orfacial characteristic information. The UI circuitry 78 may be utilizedto enter an indication of the designated destination (e.g., the phonenumber, IP address, or the like).

In an example embodiment, the sensor circuitry 80 of the communicationsdevice 70 may comprise the video camera portion 82, the force/wavesensor 84, and the microphone 86. The video camera portion 82 maycomprise a camera (or cameras) and associated equipment capable ofcapturing still images and/or video and to provide the captured stillimages and/or video to other portions of the communications device 70.In an example embodiment, the force/wave sensor 84 may comprise anaccelerometer, a tilt sensor, an acoustic sensor capable of sensingacoustic energy, an optical sensor (e.g., infrared), or any combinationthereof.

FIG. 5 is a block diagram of an example relay service server 90. In anexample embodiment, the relay service server 90 may comprise the relayservice center server 24 described herein. In an example embodiment, therelay service server 90 comprises hardware or a combination of hardwareand software. The functionality needed to facilitate initiation of acall to an emergency call center may reside in any one or combination ofrelay service servers. The relay service server 90 depicted in FIG. 5represents any appropriate entity, apparatus, or combination of entitiesor apparatuses, such as a processor, a server, a gateway, etc., or anycombination thereof. It is emphasized that the block diagram depicted inFIG. 5 is exemplary and not intended to imply a specific implementationor configuration. Thus, the relay service server 90 may be implementedin a single processor or multiple processors (e.g., single server ormultiple servers, single gateway or multiple gateways, etc.). Multipleservers may be distributed or centrally located. Multiple servers maycommunicate wirelessly, via hard wire, or a combination thereof.

In an example configuration, the relay service server 90 may compriseprocessing circuitry 92, memory circuitry 94, and input/output circuitry96. The processing circuitry 92, memory circuitry 94, and input/outputcircuitry 96 are coupled together (coupling not shown in FIG. 5) toallow communications therebetween. The processing circuitry 92 may becapable of performing functions associated with facilitating initiationof a call to an emergency call center, as described herein. For example,the processing circuitry 92 may be capable of, in conjunction with anyother portion of the relay service server 90, executing an applicationfor facilitating initiation of a call to an emergency call center,generating a non-voice message, generating a voice message,communication via a text message and/or voice message, processing areceived text message, processing a received voice message, processing aretrieved text message, processing a retrieved voice message, generatinga predetermined message, retrieving a predetermined message, processingtext messages received via the input/output circuitry 96, processingvoice messages received via the input/output circuitry 96, determiningif an emergency condition exists, or the like, or any combinationthereof. The processing circuitry 92, in conjunction with any otherportion of the relay service server 90, may provide the ability forusers to enable, disable, and configure various features of anapplication for facilitating initiation of a call to an emergency callcenter, as described herein. The processing circuitry 92, in conjunctionwith any other portion of the communications device 90, may enable therelay service server 90 to covert speech to text when it is configuredto send text messages. In an example embodiment, the processingcircuitry 92, in conjunction with any other portion of the relay serviceserver 90, may be able to convert text to speech.

The input/output circuitry 96 may capable of receiving and/or providinginformation from/to a device (e.g., communications device 14,communications device 70), other relay service servers, other relayservices, and/or emergency call centers, when facilitating initiation ofa call to an emergency call center, as described herein. Theinput/output circuitry 96 may be capable of communications with thewireless network 16, the another relay service center, another the relayservice center server, the communications device 14, the communicationsdevice 70, and/or the emergency call center 22, as described herein. Forexample, the input/output circuitry 96 may include a wirelesscommunications (e.g., 2.5G/3G/4G) SIM card. The input/output circuitry96 may be capable of receiving and/or sending video information, audioinformation, control information, image information, data, or anycombination thereof. In an example embodiment, the input/outputcircuitry 96 may be capable of receiving and/or sending information todetermine a location of a communications device (e.g., communicationsdevice 14, communications device 70). In an example configuration, theinput\output circuitry 96 may comprise a GPS receiver. In an exampleconfiguration, a geographical location may be determined through anytype of location determination system including, for example, the GlobalPositioning System (GPS), assisted GPS (A-GPS), time difference ofarrival calculations, configured constant location (in the case ofnon-moving devices), any combination thereof, or any other appropriatemeans. In various configurations, the input/output circuitry 96 mayreceive and/or provide information via any appropriate means, such as,for example, optical means (e.g., infrared), electromagnetic means(e.g., RF, WI-FI, BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g.,speaker, microphone, ultrasonic receiver, ultrasonic transmitter), orany appropriate combination thereof. In an example configuration, theinput/output circuitry may comprise a WIFI finder, a two way GPS chipsetor equivalent, or the like.

The memory circuitry 94 may store any information utilized inconjunction with facilitating initiation of a call to an emergency callcenter, as described herein. For example, the memory circuitry 94 may becapable of storing information pertaining to executing an applicationfor facilitating initiation of a call to an emergency call center,generating a non-voice message, generating a voice message,communication with a relay service center via a text message and/orvoice message, communication with an emergency call center via a textmessage and/or voice message, processing a received text message,processing a received voice message, processing a retrieved textmessage, processing a retrieved voice message, generating apredetermined message, retrieving a predetermined message, processingtext messages received via the input/output circuitry 96, processingvoice messages received via the input/output circuitry 96, determiningif an emergency condition exists, analyzing a call, maintain multi-modecommunications, or the like, as described herein, or any appropriatecombination thereof.

Depending upon the exact configuration and type of relay service server90, the memory circuitry 94 may include computer storage media that isvolatile 98 (such as dynamic RAM), non-volatile 100 (such as ROM), or acombination thereof. The relay service server 90 may include additionalstorage, in the form of computer storage media (e.g., removable storage102 and/or non-removable storage 104) including, RAM, ROM, EEPROM, tape,flash memory, smart cards, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, universal serial bus (USB)compatible memory. As described herein, a computer storage medium is anarticle of manufacture and thus not a transient signal.

The relay service server 90 also may contain communicationsconnection(s) 110 that allow the relay service server 90 to communicatewith other devices, entities, servers, or the like. A communicationsconnection(s) can comprise communication media. Communication media maybe used to communicate computer readable instructions, data structures,program modules, or other data. Communication media can include anappropriate transport mechanism or information delivery media that maybe used to transport a modulated data signal such as a carrier wave.

The relay service server 90 also may include input device(s) 106 such askeyboard, mouse, pen, voice input device, touch input device, etc.Output device(s) 108 such as a display, speakers, printer, etc. also canbe included.

Communications devices (e.g., communications device 14, communicationsdevice 70) and servers (e.g., relay service center server 24, relayservice server 90) may be part of and/or in communication with variouswireless communications networks. Some of which are described below.

FIG. 6 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichinitiation of a call to an emergency call center may be implemented. Inthe exemplary packet-based mobile cellular network environment shown inFIG. 6, there are a plurality of Base Station Subsystems (“BSS”) 600(only one is shown), each of which comprises a Base Station Controller(“BSC”) 602 serving a plurality of Base Transceiver Stations (“BTS”)such as BTSs 604, 606, and 608. BTSs 604, 606, 608, etc. are the accesspoints where users of packet-based mobile devices become connected tothe wireless network. In exemplary fashion, the packet trafficoriginating from user devices is transported via an over-the-airinterface to a BTS 608, and from the BTS 608 to the BSC 602. Basestation subsystems, such as BSS 600, are a part of internal frame relaynetwork 610 that can include Service GPRS Support Nodes (“SGSN”) such asSGSN 612 and 614. Each SGSN is connected to an internal packet network620 through which a SGSN 612, 614, etc. can route data packets to andfrom a plurality of gateway GPRS support nodes (GGSN) 622, 624, 626,etc. As illustrated, SGSN 614 and GGSNs 622, 624, and 626 are part ofinternal packet network 620. Gateway GPRS serving nodes 622, 624 and 626mainly provide an interface to external Internet Protocol (“IP”)networks such as Public Land Mobile Network (“PLMN”) 650, corporateintranets 640, or Fixed-End System (“FES”) or the public Internet 630.As illustrated, subscriber corporate network 640 may be connected toGGSN 624 via firewall 632; and PLMN 650 is connected to GGSN 624 viaboarder gateway router 634. The Remote Authentication Dial-In UserService (“RADIUS”) server 642 may be used for caller authentication whena user of a mobile cellular device calls corporate network 640.

Generally, there may be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto and umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential, or smallbusiness environments. On the other hand, umbrella cells are used tocover shadowed regions of smaller cells and fill in gaps in coveragebetween those cells.

FIG. 7 illustrates an architecture of a typical GPRS network in whichinitiation of a call to an emergency call center may be implemented. Thearchitecture depicted in FIG. 7 is segmented into four groups: users750, radio access network 760, core network 770, and interconnectnetwork 780. Users 750 comprise a plurality of end users. Note, device712 is referred to as a mobile subscriber in the description of networkshown in FIG. 7. In an example embodiment, the device depicted as mobilesubscriber 712 comprises a communications device (e.g., communicationsdevice 14, communications device 70). Radio access network 760 comprisesa plurality of base station subsystems such as BSSs 762, which includeBTSs 764 and BSCs 766. Core network 770 comprises a host of variousnetwork elements. As illustrated in FIG. 7, core network 770 maycomprise Mobile Switching Center (“MSC”) 771, Service Control Point(“SCP”) 772, gateway MSC 773, SGSN 776, Home Location Register (“HLR”)774, Authentication Center (“AuC”) 775, Domain Name Server (“DNS”) 777,and GGSN 778. Interconnect network 780 also comprises a host of variousnetworks and other network elements. As illustrated in FIG. 7,interconnect network 780 comprises Public Switched Telephone Network(“PSTN”) 782, Fixed-End System (“FES”) or Internet 784, firewall 788,and Corporate Network 789.

A mobile switching center may be connected to a large number of basestation controllers. At MSC 771, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 782 through Gateway MSC(“GMSC”) 773, and/or data may be sent to SGSN 776, which then sends thedata traffic to GGSN 778 for further forwarding.

When MSC 771 receives call traffic, for example, from BSC 766, it sendsa query to a database hosted by SCP 772. The SCP 772 processes therequest and issues a response to MSC 771 so that it may continue callprocessing as appropriate.

The HLR 774 is a centralized database for users to register to the GPRSnetwork. HLR 774 stores static information about the subscribers such asthe International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 774 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 774 is AuC 775. AuC 775 is adatabase that contains the algorithms for authenticating subscribers andincludes the associated keys for encryption to safeguard the user inputfor authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 7, whenmobile subscriber 712 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 712 to SGSN 776. The SGSN 776 queries another SGSN, towhich mobile subscriber 712 was attached before, for the identity ofmobile subscriber 712. Upon receiving the identity of mobile subscriber712 from the other SGSN, SGSN 776 requests more information from mobilesubscriber 712. This information is used to authenticate mobilesubscriber 712 to SGSN 776 by HLR 774. Once verified, SGSN 776 sends alocation update to HLR 774 indicating the change of location to a newSGSN, in this case SGSN 776. HLR 774 notifies the old SGSN, to whichmobile subscriber 712 was attached before, to cancel the locationprocess for mobile subscriber 712. HLR 774 then notifies SGSN 776 thatthe location update has been performed. At this time, SGSN 776 sends anAttach Accept message to mobile subscriber 712, which in turn sends anAttach Complete message to SGSN 776.

After attaching itself with the network, mobile subscriber 712 then goesthrough the authentication process. In the authentication process, SGSN776 sends the authentication information to HLR 774, which sendsinformation back to SGSN 776 based on the user profile that was part ofthe user's initial setup. The SGSN 776 then sends a request forauthentication and ciphering to mobile subscriber 712. The mobilesubscriber 712 uses an algorithm to send the user identification (ID)and password to SGSN 776. The SGSN 776 uses the same algorithm andcompares the result. If a match occurs, SGSN 776 authenticates mobilesubscriber 712.

Next, the mobile subscriber 712 establishes a user session with thedestination network, corporate network 789, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 712 requests access to the Access Point Name (“APN”),for example, UPS.com, and SGSN 776 receives the activation request frommobile subscriber 712. SGSN 776 then initiates a Domain Name Service(“DNS”) query to learn which GGSN node has access to the UPS.com APN.The DNS query is sent to the DNS server within the core network 770,such as DNS 777, which is provisioned to map to one or more GGSN nodesin the core network 770. Based on the APN, the mapped GGSN 778 canaccess the requested corporate network 789. The SGSN 776 then sends toGGSN 778 a Create Packet Data Protocol (“PDP”) Context Request messagethat contains necessary information. The GGSN 778 sends a Create PDPContext Response message to SGSN 776, which then sends an Activate PDPContext Accept message to mobile subscriber 712.

Once activated, data packets of the call made by mobile subscriber 712can then go through radio access network 760, core network 770, andinterconnect network 780, in a particular fixed-end system or Internet784 and firewall 788, to reach corporate network 789.

FIG. 8 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within which initiation of a call to anemergency call center may be implemented. As illustrated, thearchitecture of FIG. 8 includes a GSM core network 801, a GPRS network830 and an IP multimedia network 838. The GSM core network 801 includesa Mobile Station (MS) 802, at least one Base Transceiver Station (BTS)804 and a Base Station Controller (BSC) 806. The MS 802 is physicalequipment or Mobile Equipment (ME), such as a mobile phone or a laptopcomputer that is used by mobile subscribers, with a Subscriber identityModule (SIM) or a Universal Integrated Circuit Card (UICC). The SIM orUICC includes an International Mobile Subscriber Identity (IMSI), whichis a unique identifier of a subscriber. The BTS 804 is physicalequipment, such as a radio tower, that enables a radio interface tocommunicate with the MS. Each BTS may serve more than one MS. The BSC806 manages radio resources, including the BTS. The BSC may be connectedto several BTSs. The BSC and BTS components, in combination, aregenerally referred to as a base station (BSS) or radio access network(RAN) 803.

The GSM core network 801 also includes a Mobile Switching Center (MSC)808, a Gateway Mobile Switching Center (GMSC) 810, a Home LocationRegister (HLR) 812, Visitor Location Register (VLR) 814, anAuthentication Center (AuC) 818, and an Equipment Identity Register(EIR) 816. The MSC 808 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC810 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 820. Thus, the GMSC 810 provides interworkingfunctionality with external networks.

The HLR 812 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 812 also contains the current location of each MS. The VLR 814 is adatabase that contains selected administrative information from the HLR812. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 812 and the VLR 814,together with the MSC 808, provide the call routing and roamingcapabilities of GSM. The AuC 816 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 818 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 809 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 802. A PushProxy Gateway (PPG) 811 is used to “push” (i.e., send without asynchronous request) content to the MS 802. The PPG 811 acts as a proxybetween wired and wireless networks to facilitate pushing of data to theMS 802. A Short Message Peer to Peer (SMPP) protocol router 813 isprovided to convert SMS-based SMPP messages to cell broadcast messages.SMPP is a protocol for exchanging SMS messages between SMS peer entitiessuch as short message service centers. The SMPP protocol is often usedto allow third parties, e.g., content suppliers such as newsorganizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 802 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 804 and the BSC 806.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 830 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 832, a cell broadcast and a GatewayGPRS support node (GGSN) 834. The SGSN 832 is at the same hierarchicallevel as the MSC 808 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 802. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 817 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 834 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 836. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network836, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 830 can be designed to operate in three network operationmodes (NOM1, NOM2 and NOM3). A network operation mode of a GPRS networkis indicated by a parameter in system information messages transmittedwithin a cell. The system information messages dictates a MS where tolisten for paging messages and how to signal towards the network. Thenetwork operation mode represents the capabilities of the GPRS network.In a NOM1 network, a MS can receive pages from a circuit switched domain(voice call) when engaged in a data call. The MS can suspend the datacall or take both simultaneously, depending on the ability of the MS. Ina NOM2 network, a MS may not receive pages from a circuit switcheddomain when engaged in a data call, since the MS is receiving data andis not listening to a paging channel. In a NOM3 network, a MS canmonitor pages for a circuit switched network while received data andvice versa.

The IP multimedia network 838 was introduced with 3GPP Release 8, andincludes an IP multimedia subsystem (IMS) 840 to provide rich multimediaservices to end users. A representative set of the network entitieswithin the IMS 840 are a call/session control function (CSCF), a mediagateway control function (MGCF) 846, a media gateway (MGW) 848, and amaster subscriber database, called a home subscriber server (HSS) 850.The HSS 850 may be common to the GSM network 801, the GPRS network 830as well as the IP multimedia network 838.

The IP multimedia system 840 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)843, a proxy CSCF (P-CSCF) 842, and a serving CSCF (S-CSCF) 844. TheP-CSCF 842 is the MS's first point of contact with the IMS 840. TheP-CSCF 842 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 842 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 843, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 843 may contact asubscriber location function (SLF) 845 to determine which HSS 850 to usefor the particular subscriber, if multiple HSS's 850 are present. TheS-CSCF 844 performs the session control services for the MS 802. Thisincludes routing originating sessions to external networks and routingterminating sessions to visited networks. The S-CSCF 844 also decideswhether an application server (AS) 852 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 850 (or other sources, such as an application server 852). TheAS 852 also communicates to a location server 856 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 802.

The HSS 850 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 850, a subscriber location function providesinformation on the HSS 850 that contains the profile of a givensubscriber.

The MGCF 846 provides interworking functionality between SIP sessioncontrol signaling from the IMS 840 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 848 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 848 alsocommunicates with other IP multimedia networks 854.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 9 illustrates a PLMN block diagram view of an exemplaryarchitecture in which initiation of a call to an emergency call centermay be incorporated. Mobile Station (MS) 901 is the physical equipmentused by the PLMN subscriber. In one illustrative embodiment,communications device 40 may serve as Mobile Station 901. Mobile Station901 may be one of, but not limited to, a cellular telephone, a cellulartelephone in combination with another electronic device or any otherwireless mobile communication device.

Mobile Station 901 may communicate wirelessly with Base Station System(BSS) 910. BSS 910 contains a Base Station Controller (BSC) 911 and aBase Transceiver Station (BTS) 912. BSS 910 may include a single BSC911/BTS 912 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 910 is responsible for communicating withMobile Station 901 and may support one or more cells. BSS 910 isresponsible for handling cellular traffic and signaling between MobileStation 901 and Core Network 940. Typically, BSS 910 performs functionsthat include, but are not limited to, digital conversion of speechchannels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 901 may communicate wirelessly with RadioNetwork System (RNS) 920. RNS 920 contains a Radio Network Controller(RNC) 921 and one or more Node(s) B 922. RNS 920 may support one or morecells. RNS 920 may also include one or more RNC 921/Node B 922 pairs oralternatively a single RNC 921 may manage multiple Nodes B 922. RNS 920is responsible for communicating with Mobile Station 901 in itsgeographically defined area. RNC 921 is responsible for controlling theNode(s) B 922 that are connected to it and is a control element in aUMTS radio access network. RNC 921 performs functions such as, but notlimited to, load control, packet scheduling, handover control, securityfunctions, as well as controlling Mobile Station 901's access to theCore Network (CN) 940.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 930 is aradio access network that provides wireless data communications forMobile Station 901 and User Equipment 902. E-UTRAN 930 provides higherdata rates than traditional UMTS. It is part of the Long Term Evolution(LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 930 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 931 and E-UTRAN Node B (eNB) 932. E-UTRAN 930 may contain one ormore eNBs. User Equipment 902 may be any user device capable ofconnecting to E-UTRAN 930 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 930. The improvedperformance of the E-UTRAN 930 relative to a typical UMTS network allowsfor increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 9 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 901 may communicate with any or all of BSS 910,RNS 920, or E-UTRAN 930. In a illustrative system, each of BSS 910, RNS920, and E-UTRAN 930 may provide Mobile Station 901 with access to CoreNetwork 940. The Core Network 940 may include of a series of devicesthat route data and communications between end users. Core Network 940may provide network service functions to users in the Circuit Switched(CS) domain, the Packet Switched (PS) domain or both. The CS domainrefers to connections in which dedicated network resources are allocatedat the time of connection establishment and then released when theconnection is terminated. The PS domain refers to communications anddata transfers that make use of autonomous groupings of bits calledpackets. Each packet may be routed, manipulated, processed or handledindependently of all other packets in the PS domain and does not requirededicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 941 is part of CoreNetwork 940, and interacts with Visitor Location Register (VLR) andMobile-Services Switching Center (MSC) Server 960 and Gateway MSC Server961 in order to facilitate Core Network 940 resource control in the CSdomain. Functions of CS-MGW 941 include, but are not limited to, mediaconversion, bearer control, payload processing and other mobile networkprocessing such as handover or anchoring. CS-MGW 940 may receiveconnections to Mobile Station 901 through BSS 910, RNS 920 or both.

Serving GPRS Support Node (SGSN) 942 stores subscriber data regardingMobile Station 901 in order to facilitate network functionality. SGSN942 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 942 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 944 address for each GGSN where an active PDPexists. GGSN 944 may implement a location register function to storesubscriber data it receives from SGSN 942 such as subscription orlocation information.

Serving Gateway (S-GW) 943 is an interface which provides connectivitybetween E-UTRAN 930 and Core Network 940. Functions of S-GW 943 include,but are not limited to, packet routing, packet forwarding, transportlevel packet processing, event reporting to Policy and Charging RulesFunction (PCRF) 950, and mobility anchoring for inter-network mobility.PCRF 950 uses information gathered from S-GW 943, as well as othersources, to make applicable policy and charging decisions related todata flows, network resources and other network administrationfunctions. Packet Data Network Gateway (PDN-GW) 945 may provideuser-to-services connectivity functionality including, but not limitedto, network-wide mobility anchoring, bearer session anchoring andcontrol, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 963 is a database for user information, andstores subscription data regarding Mobile Station 901 or User Equipment902 for handling calls or data sessions. Networks may contain one HSS963 or more if additional resources are required. Exemplary data storedby HSS 963 include, but is not limited to, user identification,numbering and addressing information, security information, or locationinformation. HSS 963 may also provide call or session establishmentprocedures in both the PS and CS domains.

The VLR/MSC Server 960 provides user location functionality. When MobileStation 901 enters a new network location, it begins a registrationprocedure. A MSC Server for that location transfers the locationinformation to the VLR for the area. A VLR and MSC Server may be locatedin the same computing environment, as is shown by VLR/MSC Server 960, oralternatively may be located in separate computing environments. A VLRmay contain, but is not limited to, user information such as the IMSI,the Temporary Mobile Station Identity (TMSI), the Local Mobile StationIdentity (LMSI), the last known location of the mobile station, or theSGSN where the mobile station was previously registered. The MSC servermay contain information such as, but not limited to, procedures forMobile Station 901 registration or procedures for handover of MobileStation 901 to a different section of the Core Network 940. GMSC Server961 may serve as a connection to alternate GMSC Servers for other mobilestations in larger networks.

Equipment Identity Register (EIR) 962 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 901. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 901 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 962, preventing its use on the network. Mobility ManagementEntity (MME) 964 is a control node which may track Mobile Station 901 orUser Equipment 902 if the devices are idle. Additional functionality mayinclude the ability of MME 964 to contact an idle Mobile Station 901 orUser Equipment 902 if retransmission of a previous session is required.

While example embodiments of initiating a call to an emergency callcenter have been described in connection with various computingdevices/processors, the underlying concepts can be applied to anycomputing device, processor, and/or system capable of facilitatinginitiation of a call to an emergency call center as described herein.The methods and apparatuses for initiating a call to an emergency callcenter, or certain aspects or portions thereof, can take the form ofprogram code (i.e., instructions) embodied in tangible storage mediahaving a physical structure, such as floppy diskettes, CD-ROMs, harddrives, or any other machine-readable storage medium having a physicaltangible structure (computer-readable storage medium), wherein, when theprogram code is loaded into and executed by a machine, such as acomputer, the machine becomes an apparatus for facilitating initiationof a call to an emergency call center. A computer-readable storagemedium, as described herein is an article of manufacture, and thus, notto be construed as a transient signal. In the case of program codeexecution on programmable computers, the computing device will generallyinclude a processor, a storage medium readable by the processor(including volatile and non-volatile memory and/or storage elements), atleast one input device, and at least one output device. The program(s)can be implemented in assembly or machine language, if desired. Thelanguage can be a compiled or interpreted language, and combined withhardware implementations.

The methods and apparatuses for initiating a call to an emergency callcenter may be practiced via communications embodied in the form ofprogram code that is transmitted over some transmission medium, such asover electrical wiring or cabling, through fiber optics, wherein, whenthe program code is received and loaded into and executed by a machine,such as an EPROM, a gate array, a programmable logic device (PLD), aclient computer, or the like, the machine becomes an apparatus forfacilitating initiation of a call to an emergency call center. Whenimplemented on a general-purpose processor, the program code combineswith the processor to provide a unique apparatus that operates to invokethe functionality for initiating a call to an emergency call center.

While initiating a call to an emergency call center has been describedin connection with the various embodiments of the various figures, it isto be understood that other similar embodiments can be used ormodifications and additions can be made to the described embodiments forinitiating a call to an emergency call center. For example, one skilledin the art will recognize that initiating a call to an emergency callcenter as described in the present application may apply to anyenvironment, whether wired or wireless, and may be applied to any numberof devices connected via a communications network and interacting acrossthe network. Therefore, initiating a call to an emergency call centershould not be limited to any single embodiment, but rather should beconstrued in breadth and scope in accordance with the appended claims.

1. A method comprising: providing, by a communications device, amessage; receiving, by the communications device, a first call, wherein:the first call is indicative of originating from a recipient of themessage; and receipt, by itself, based on a telephone number of thefirst call, is indicative of a determination that an emergency conditionexists; placing, from the communications device, the first call on hold;initiating, from the communications device, a second call; andestablishing a conference call comprising the first call and the secondcall.
 2. The method of claim 1, wherein the determination that anemergency condition exists is determined by the recipient of themessage.
 3. The method of claim 1, further comprising communicating witha recipient of the second call via the recipient of the message.
 4. Themethod of claim 1, wherein the message is a non-voice message.
 5. Themethod of claim 1, wherein the conference call is a voice call.
 6. Themethod of claim 1, further comprising maintaining, during the conferencecall, multi-mode communications, wherein the multi-mode communicationscomprises: two-way person-to-person non-voice communications with therecipient of the message; and two-way person-to-person voicecommunications via the conference call.
 7. The method of claim 1,wherein the recipient of message comprises a relay service.
 8. Themethod of claim 1, wherein a recipient of the second call comprises anemergency call center.
 9. A device comprising: memory comprisingexecutable instructions; and a processor in communications with thememory, the processor configured to execute the instructions to performoperations comprising: providing a message; receiving a first call,wherein: the first call is indicative of originating from a recipient ofthe message; and receipt, by itself, based on a telephone number of thefirst call_(s) is indicative of a determination that an emergencycondition exists; placing the first call on hold; initiating a secondcall; and establishing a conference call comprising the first call andthe second call.
 10. The device of claim 9, wherein the determinationthat an emergency condition exists is determined by the recipient of themessage.
 11. The device of claim 9, the operations further comprisingcommunicating with a recipient of the second call via the recipient ofthe message.
 12. The device of claim 9, wherein the message is anon-voice message.
 13. The device of claim 9, wherein the conferencecall is a voice call.
 14. The device of claim 9, the operations furthercomprising maintaining, during the conference call, multi-modecommunications, wherein the multi-mode communications comprises: two-wayperson-to-person non-voice communications with the recipient of themessage; and two-way person-to-person voice communications via theconference call.
 15. The device of claim 9, wherein the recipient ofmessage comprises a relay service.
 16. The device of claim 9, wherein arecipient of the second call comprises an emergency call center.
 17. Thedevice of claim 9, wherein the device comprises a mobile communicationsdevice.
 18. A computer-readable storage medium having executableinstructions stored thereon that when executed by a processor performoperations comprising: providing a message; receiving a first call,wherein: the first call is indicative of originating from a recipient ofthe message; and receipt, by itself, based on a telephone number of thefirst call, is indicative of a determination that an emergency conditionexists; placing the first call on hold; initiating a second call; andestablishing a conference call comprising the first call and the secondcall.
 19. The computer-readable storage medium of claim 18, theoperations further comprising communicating with a recipient of thesecond call via the recipient of the message.
 20. The computer-readablestorage medium of claim 18, further comprising maintaining, during theconference call, multi-mode communications, wherein the multi-modecommunications comprises: two-way person-to-person non-voicecommunications with the recipient of the message; and two-wayperson-to-person voice communications via the conference call.